home *** CD-ROM | disk | FTP | other *** search
- Path: news.crystalball.com!news
- From: Larry Weiss <lfw@oc.com>
- Newsgroups: comp.lang.c
- Subject: Re: 16bit vs. 32bit
- Date: Sat, 30 Mar 1996 14:45:11 -0600
- Organization: ...
- Message-ID: <315D9D57.5FED@oc.com>
- References: <4iui27$egk@news.netam.net> <DovvHG.3DK@eskimo.com> <315845E6.64FC@oc.com> <Dp3EH0.I92@eskimo.com>
- NNTP-Posting-Host: external.oc.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0 (Win16; I)
-
- Steve Summit wrote:
- > In article <315845E6.64FC@oc.com>, Larry Weiss <lfw@oc.com> wrote:
- > > How do you know how large your arrays could be without some
- > > consideration of the executing machine(s), perhaps done by
- > > inspecting size_t ?
- >
- > If you're a nutso flaming Standard-thumping language lawyer, you
- > know that the Standard doesn't guarantee that individual objects
- > can be larger than 32k, and you just don't ever try to allocate
- > large, contiguous arrays.
-
- Thanks Steve for the reply. I'm trying on my magic language-lawyer hat
- right now, but it doesn't help, cause I'm still overlooking the 32K reference.
- Is it contained in a certain Clause that you can cite? I thought that
- there was a limitation like that, but I'm going "nutso" trying to find it.
-
- Is this one of those minimal maxima type values?
-